2.0 System Requirements
Go to the Table Of Contents, go back to 1.0 Introduction or go forward to 3.0 Installation.
2.1 Hardware requirements
- any colour capable Macintosh computer or compatible. Essentially, any Mac with a 68020, 68030, 68040 or PowerPC series microprocessor. You do not need to have a colour screen.
- at least 1 Mb of free memory
- a network connection, which can consist of any of the following:
- a SLIP or PPP connection to any internet service provider or equivalent
- a LocalTalk or EtherTalk connection to an IP gateway
- an Ethernet connection to either a TCP/IP network or some kind of TCP/IP gateway
2.2 Recommended hardware
- at least 2Mb of free memory (if you open several connections at the same time)
- a PowerBook (640 x 400) or 14" monitor (640 x 480) or better. Better yet, two monitors :-)
2.3 Software requirements
- EITHER System Software 7.0 or later with the Thread Manager 2.1 or later extension OR MacOS 7.5 or later (which has the Thread Manager extension built-in).
- EITHER MacTCP 2.0.4 or later OR Open Transport 1.1.1 or later.
- if you are using a modem to connect to the internet, you should have the appropriate network software installed for SLIP or PPP access, for example, "MacPPP", "FreePPP" or "Open Transport/PPP 1.0".
2.4 Recommended software
- MacOS 7.5.5 or later, because it has many improvements/bug fixes and includes Drag and Drop support.
- Open Transport 1.1.1 or later, because it actually works and is quite stable (it used to be that OT was called "Broken Transport" but this is no longer the case - it is now more stable than MacTCP 2.0.6 in our experience).
- Internet Config 1.4 or later (included in this package)
2.5 Compatibility
There is only one known problem at this time: NetFinder will not be able to be started if the Text Encoding Converter (part of MacOS 8) is enabled but the "Text Encodings" folder is empty. If you attempt to start NetFinder in this situation, a dialog will appear informing you that 'NetFinder could not be opened because ">>TextCommon<<" could not be found.' The solution is to put at least one text encoding extension into the "Text Encodings" folder.
If you suspect any other incompatibilities, please contact the authors about it. We will try to find a solution if it is possible.
Go to the Table Of Contents, go back to 1.0 Introduction or go forward to 3.0 Installation.
Copyright © 1997, Peter Li and Vincent Tan.